Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the test result output path for TemplateIntegrationTests #2845

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Numpsy
Copy link
Contributor

@Numpsy Numpsy commented Dec 24, 2024

Description

I noticed when having a poke at the .NET 8 CI test failures that the 'Fake.DotNet.Cli.IntegrationTests' test results file isn't being published into the CI as the restults file is getting put under the integration tests folder rather than under the root results folder with the other 3 result xml files - so this is an attempt to fix that by using the same root results folder as the other test project runs

targetDir
"bin/Release/net6.0/Fake.DotNet.Cli.IntegrationTests.dll"
root
("src" </> "test" </> "Fake.DotNet.Cli.IntegrationTests" </> "bin" </> "Release" </> "net6.0" </> "Fake.DotNet.Cli.IntegrationTests.dll")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pulled the change out of a version of the .NET 8 branch, so it picked up the change to avoid hard coded path separators as well

Copy link
Contributor

github-actions bot commented Dec 24, 2024

Test Results

   12 files  + 3     12 suites  +3   49m 13s ⏱️ + 1m 14s
  451 tests + 8    450 ✅ + 7  1 💤 +1  0 ❌ ±0 
1 287 runs  +24  1 284 ✅ +21  3 💤 +3  0 ❌ ±0 

Results for commit fcaed66. ± Comparison against base commit 78a2562.

♻️ This comment has been updated with latest results.

@xperiandri xperiandri force-pushed the TemplateIntegrationTests_path branch from 42ab2c8 to 6df8003 Compare January 8, 2025 19:17
@xperiandri xperiandri force-pushed the TemplateIntegrationTests_path branch from 6df8003 to fcaed66 Compare January 8, 2025 21:31
@xperiandri
Copy link
Collaborator

@Numpsy should any previous fixes or this be documented in the release notes?

@Numpsy
Copy link
Contributor Author

Numpsy commented Jan 8, 2025

@xperiandri #2839 maybe? (this one is just in the tests)

@xperiandri
Copy link
Collaborator

Yes, not very important for consumers but makes sense to mention

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants